Skip to content

Conversation

@bjorn3
Copy link
Member

@bjorn3 bjorn3 commented Oct 23, 2025

This allows getting rid of all the argument mangling hacks as well as the exported_non_generic_symbols override hack by doing cargo build instead of cargo check. This is also a prerequisite for using native jit mode support in miri that I hope to add to rustc in the future to be used with cg_clif too.

@rustbot rustbot added the S-waiting-on-author Status: Waiting for the PR author to address review comments label Oct 23, 2025
/// Also disable the MIR pass that inserts an alignment check on every pointer dereference. Miri
/// does that too, and with a better error message.
pub const MIRI_DEFAULT_ARGS: &[&str] = &[
"-Zcodegen-backend=dummy",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dummy codegen backend is a builtin codegen backend that is only capable of emitting rlibs containing the crate metadata. For every other crate type it emits an error after codegen. This is fine for miri as for --crate-type bin, miri exits before codegen.

bors added a commit to rust-lang/rust that referenced this pull request Oct 28, 2025
…apkin

Allow codegen backends to indicate which crate types they support

This way cargo will drop the unsupported crate types for crates that
specify multiple crate types.

This is a prerequisite for rust-lang/miri#4648.
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Oct 28, 2025
…, r=WaffleLapkin

Allow codegen backends to indicate which crate types they support

This way cargo will drop the unsupported crate types for crates that
specify multiple crate types.

This is a prerequisite for rust-lang/miri#4648.
rust-timer added a commit to rust-lang/rust that referenced this pull request Oct 28, 2025
Rollup merge of #148177 - bjorn3:codegen_backend_crate_types, r=WaffleLapkin

Allow codegen backends to indicate which crate types they support

This way cargo will drop the unsupported crate types for crates that
specify multiple crate types.

This is a prerequisite for rust-lang/miri#4648.
@bjorn3 bjorn3 force-pushed the dummy_backend branch 2 times, most recently from ac1e234 to ef6aed4 Compare October 29, 2025 12:23
@rustbot

This comment has been minimized.

matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Oct 29, 2025
…es, r=JonathanBrouwer

Handle default features and -Ctarget-features in the dummy backend

This prevents a warning about ABI relevant target features not being set on x86 and arm. In addition it is required for miri to report correct features in is_*_feature_detected!() if miri switches to the dummy backend.

Required for rust-lang/miri#4648
Zalathar added a commit to Zalathar/rust that referenced this pull request Oct 30, 2025
…es, r=JonathanBrouwer

Handle default features and -Ctarget-features in the dummy backend

This prevents a warning about ABI relevant target features not being set on x86 and arm. In addition it is required for miri to report correct features in is_*_feature_detected!() if miri switches to the dummy backend.

Required for rust-lang/miri#4648
jhpratt added a commit to jhpratt/rust that referenced this pull request Oct 30, 2025
…es, r=JonathanBrouwer

Handle default features and -Ctarget-features in the dummy backend

This prevents a warning about ABI relevant target features not being set on x86 and arm. In addition it is required for miri to report correct features in is_*_feature_detected!() if miri switches to the dummy backend.

Required for rust-lang/miri#4648
rust-timer added a commit to rust-lang/rust that referenced this pull request Oct 30, 2025
Rollup merge of #148253 - bjorn3:dummy_backend_target_features, r=JonathanBrouwer

Handle default features and -Ctarget-features in the dummy backend

This prevents a warning about ABI relevant target features not being set on x86 and arm. In addition it is required for miri to report correct features in is_*_feature_detected!() if miri switches to the dummy backend.

Required for rust-lang/miri#4648
@bjorn3 bjorn3 force-pushed the dummy_backend branch 4 times, most recently from a4a79ee to ff9ef3b Compare October 30, 2025 15:00
@bjorn3
Copy link
Member Author

bjorn3 commented Oct 30, 2025

Almost there. With rust-lang/rust#148177 and rust-lang/rust#148253 merged, the entire miri test suite passes after blessing a single change to a query cycle error. Doctests are broken however due to those requiring a check build for bin crates first, which the dummy codegen backend doesn't yet allow. Opened rust-lang/rust#148299 for this.

@bjorn3
Copy link
Member Author

bjorn3 commented Oct 30, 2025

I hadn't noticed the cargo-miri-test test suite before. It currently has trouble with non-rlib/bin crate types. In particular cargo thinks it needs to build crates only available as cdylib (despite those never being usable) and the dropping unsupported crate type warnings have a non-deterministic order for some reason (edit: I think this is because of non-deterministic order in which rustc is executed. I assumed cargo would skip unsupported --crate-type args and report those warnings itself, but it seems like cargo just forwards them to rustc and expects rustc to produce the warnings.).

bors added a commit to rust-lang/rust that referenced this pull request Oct 30, 2025
Allow check builds with binaries for the dummy codegen backend

This is likely the last part necessary for rust-lang/miri#4648. Miri needs to be able to do a regular check build for compile_fail doc tests to work.
@bjorn3 bjorn3 force-pushed the dummy_backend branch 2 times, most recently from 95b1a48 to cad7423 Compare October 31, 2025 12:45
@bjorn3 bjorn3 marked this pull request as ready for review November 3, 2025 18:21
@rustbot
Copy link
Collaborator

rustbot commented Nov 3, 2025

Thank you for contributing to Miri!
Please remember to not force-push to the PR branch except when you need to rebase due to a conflict or when the reviewer asks you for it.

@rustbot rustbot added S-waiting-on-review Status: Waiting for a review to complete and removed S-waiting-on-author Status: Waiting for the PR author to address review comments labels Nov 3, 2025
makai410 pushed a commit to makai410/rustc_public that referenced this pull request Nov 4, 2025
…athanBrouwer

Handle default features and -Ctarget-features in the dummy backend

This prevents a warning about ABI relevant target features not being set on x86 and arm. In addition it is required for miri to report correct features in is_*_feature_detected!() if miri switches to the dummy backend.

Required for rust-lang/miri#4648
Copy link
Member

@RalfJung RalfJung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

src/bin/miri.rs Outdated
if config.opts.prints.is_empty() && self.target_crate {
// Avoid warnings about unsupported crate types
#[allow(rustc::bad_opt_access)]
config.opts.crate_types.retain(|&c| c == CrateType::Executable || c == CrateType::Rlib);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably only do this for target crates?

What happens if the list of crate types is empty after the filtering?

Also, why is it okay to allow bad_opt_access here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably only do this for target crates?

This is gated behind if self.target_crate.

What happens if the list of crate types is empty after the filtering?

Currently rustc treats that as implicit --crate-type lib, but in any case it shouldn't be possible to get an empty list here. Cargo will error if none of the crate types are bin or rlib as the dummy codegen backend only lists those crate types as supported.

Also, why is it okay to allow bad_opt_access here?

This is long before the TyCtxt gets created that you are normally supposed to access crate_types through.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently rustc treats that as implicit --crate-type lib, but in any case it shouldn't be possible to get an empty list here. Cargo will error if none of the crate types are bin or rlib as the dummy codegen backend only lists those crate types as supported.

Please add an assertion then.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently rustc treats that as implicit --crate-type lib

Actually, it treats it as --crate-type bin just like if the user didn't pass --crate-type at all. I got it confused with the behavior when --crate-type is present on the cli, but all listed crate types are unsupported by the target or codegen backend.

In any case I added an assertion.

@rustbot rustbot added S-waiting-on-author Status: Waiting for the PR author to address review comments and removed S-waiting-on-review Status: Waiting for a review to complete labels Nov 5, 2025
@bjorn3 bjorn3 force-pushed the dummy_backend branch 2 times, most recently from ba4b99f to dae6966 Compare November 5, 2025 10:58
@bjorn3
Copy link
Member Author

bjorn3 commented Nov 5, 2025

@rustbot ready

@rustbot rustbot added S-waiting-on-review Status: Waiting for a review to complete and removed S-waiting-on-author Status: Waiting for the PR author to address review comments labels Nov 5, 2025
@RalfJung
Copy link
Member

RalfJung commented Nov 6, 2025

This looks great, thanks! Please squash the commits using ./miri squash. Then write @rustbot ready after you force-pushed the squashed PR.

@rustbot author

@rustbot rustbot added S-waiting-on-author Status: Waiting for the PR author to address review comments and removed S-waiting-on-review Status: Waiting for a review to complete labels Nov 6, 2025
This allows getting rid of all the argument mangling hacks as well as
the exported_non_generic_symbols override hack by doing cargo build
instead of cargo check. This is also a prerequisite for using native jit
mode support in miri that I hope to add to rustc in the future to be
used with cg_clif too.
@bjorn3
Copy link
Member Author

bjorn3 commented Nov 6, 2025

@rustbot ready

@rustbot rustbot added S-waiting-on-review Status: Waiting for a review to complete and removed S-waiting-on-author Status: Waiting for the PR author to address review comments labels Nov 6, 2025
@RalfJung
Copy link
Member

RalfJung commented Nov 6, 2025

All right, let's see how well this works :)

@RalfJung RalfJung enabled auto-merge November 6, 2025 21:16
@RalfJung RalfJung added this pull request to the merge queue Nov 6, 2025
Merged via the queue into rust-lang:master with commit 220dae5 Nov 6, 2025
13 checks passed
@rustbot rustbot removed the S-waiting-on-review Status: Waiting for a review to complete label Nov 6, 2025
@bjorn3 bjorn3 deleted the dummy_backend branch November 6, 2025 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants